Remote access authentication and authorization

ABSTRACT

Features are disclosed for accurately authenticating a delivery agent for unattended delivery of an item. The systems and methods described confirm the location of the delivery agent and proximity to the delivery location using short range wireless communications between a monitoring device at the delivery location and a communication device associated with the delivery agent. Access may also be conditioned on user specified “do not disturb” rules indicating when remote access is authorized. The authentication may be dynamically assessed such as based on a type of item being delivered.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/389,726 filed on Apr. 19, 2019 entitled “REMOTE ACCESS AUTHENTICATIONAND AUTHORIZATION,” which is a continuation of U.S. patent applicationSer. No. 16/012,204 filed on Jun. 19, 2018 entitled “REMOTE ACCESSAUTHENTICATION AND AUTHORIZATION,” now U.S. Pat. No. 10,297,095, whichis a continuation of U.S. patent application Ser. No. 15/659,059 filedon Jul. 25, 2017 entitled “REMOTE ACCESS AUTHENTICATION ANDAUTHORIZATION,” now U.S. Pat. No. 10,019,860, the disclosure of each ofwhich is hereby incorporated by reference in its entirety. Furthermore,any and all priority claims identified in the Application Data Sheet, orany correction thereto, are hereby incorporated by reference under 37C.F.R. § 1.57.

BACKGROUND

Item deliveries often require the presence of a person to receive theitem. If no one is available to receive the item, subsequent attemptsmay be made to deliver the item. Alternatively, the item may be left ator near the physical delivery location. In this case, the item may bedamaged such as by weather or wildlife. The item may be stolen as itwaits for the intended recipient. Thus, leaving an item unattended in anunsecured location can result in inefficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of various inventive features will now be described withreference to the following drawings. Throughout the drawings, referencenumbers may be re-used to indicate correspondence between referencedelements. The drawings are provided to illustrate example embodimentsdescribed herein and are not intended to limit the scope of thedisclosure.

FIG. 1 is a block diagram showing an example environment including aremote access service.

FIG. 2 is a diagram showing illustrative communication paths betweendevices within a remote access system.

FIG. 3 is a diagram showing illustrative messaging between deviceswithin a remote access system.

FIG. 4 is a flow diagram depicting an example method of remote accessauthentication and authorization.

FIG. 5 is a flow diagram depicting an example method of permittingaccess to a delivery location based at least in part on monitoringstatus.

FIG. 6 is a block diagram of an illustrative computing device that mayimplement one or more of the access control features described.

DETAILED DESCRIPTION

Another solution for unattended item delivery may be to allow access tothe delivery location, but such a solution requires a safe, secure, andefficient mechanism for ensuring only authorized parties are grantedaccess.

Described are features for an unattended delivery to provide remoteaccess with secure authentication and authorization. The solutionensures delivery integrity by verifying, in real-time, that the expecteditem, carried by an expected agent, is located at an expected location,with expected monitoring, before granting access to the deliverylocation.

For example, a delivery agent may arrive at a delivery location. Thedelivery agent may scan the item using a delivery device. A remoteaccess system may confirm the delivery agent's proximity to the deliverylocation. For example, the proximity may be confirmed by a uniqueidentifier transmitted using a personal area network of limited rangesuch as a BLUETOOTH® 4.0 Low Energy communication. The unique identifiermay be transmitted to the delivery device by a monitoring device at thedelivery location such as a camera. This unique identifier may betransmitted from the delivery device to a remote access server toconfirm the proximity of the delivery device. The identifier may betransmitted using a wide area network such as a cellular network or anInternet connection.

After confirming the proximity, the delivery device may present aninterface including an instruction to knock or ring the bell at thedelivery location. If the recipient is at the delivery location, aface-to-face delivery may be achieved. If the recipient is not at thedelivery location, in the prior systems as discussed above, the deliveryagent may forego delivery or leave the package, unattended andunsecured, at the delivery location. In the innovative embodimentsdescribed, another option is available. The delivery agent may activatea control element (e.g., button) on an interface presented via thedelivery device. The control element may cause the delivery device totransmit a request to unlock the delivery location. This request may betransmitted to the remote access server via the wide area network (e.g.,a cellular network).

The remote access server may validate the request to confirm, forexample, that the item corresponds to the delivery location. If the itemis at the correct location, the remote access server may transmit acontrol message to cause the monitoring device to start collecting data(e.g., recording). The control message may be transmitted to themonitoring device via a wide area network. In some implementations, themonitoring device may be connected to a home WI-FI® network or otherIEEE 802.11 standards based wireless network, which in turn is connectedto the wide area network.

After receiving a message confirming the monitoring device has changedstate (e.g., started recording), the remote access system may transmit acontrol message to cause a lock or other security device to unlock,disengage, or otherwise release thereby permitting access to thedelivery location. The control message may be transmitted to themonitoring device via the wide area network. The monitoring device may,in turn, transmit the unlock command or release command to the lock. Theunlock command may be transmitted via a local area network, such as aZIGBEE™ or Z-WAVE® network, to unlock the door.

The delivery agent may then place the item inside the delivery location(e.g., home, office, delivery bin, locker, shed, etc.). The monitoringdevice may be configured to capture data of the agent as she is enteringthe location, placing the item, and exiting the location. Once the itemis placed, the delivery agent may activate a control element on theinterface of the delivery device that causes the delivery device totransmit a request to secure the delivery location. This request may betransmitted to the remote access server via the wide area network.

The remote access server may transmit a lock command to secure thedelivery location. In some implementations, the lock command may betransmitted to the monitoring device via a wide area network. In suchimplementations, the monitoring device may transmit the lock command tothe lock via the local area network (e.g., Z-WAVE®, ZIGBEE™, or othernetwork based on the IEEE 802.15.4 standard) to secure the deliverylocation. After confirming that the delivery location is secure (e.g.,the door is in a locked status), the remote access server may transmit acontrol command to the monitoring device to via the wide area network tostop monitoring.

In some implementations, the remote access server may transmitnotification messages to a communication device associated with arecipient to indicate the delivery status. For example, a message may betransmitted denoting the item was delivered with a link to watch a videoclip of the delivery.

By requiring that a delivery agent scans a package to gain entry, inconjunction with the confirmation of delivery location for the item andproximity to the delivery location, unattended access to a securedlocation can be safely provided. In some implementations, a time elementmay be applied to control when remote access may be granted (e.g.,delivery must be between 2:00 and 4:00). Such timing constraints may beapplied by the remote access server in assessing whether to issue theunlock command. A recipient may specify specific times for delivery ordesignate “do not disturb/enter” times. The preferences may be for thedelivery location, for a specific item, or for time duration (e.g., onvacation). If a request to unlock is received during such times or foran item associated with such times, the system may deny access.

FIG. 1 is a block diagram showing an example environment including aremote access service. The environment 100 may include a delivery device122. The delivery device 122 may be an electronic communication deviceconfigured to transmit machine readable messages via multiple wirelesscommunication protocols. Non-limiting examples of the delivery device122 include a personal computing device, laptop computing device, handheld computing device, mobile device (e.g., mobile phones or tabletcomputing devices), wearable device configured with network access andprogram execution capabilities (e.g., “smart eyewear” or “smartwatches”), wireless device, electronic reader, or some other portableelectronic device or appliance. The messages may be formatted accordingto a standardized protocol such as TCP/IP, HTTP, FTP, or the like. Thetransmission may be sent via wireless or hybrid wired-wireless networks.

A delivery agent 120 may interact with one or more interfaces presentedvia the delivery device 122. The interfaces may include control elementsto receive input or adjust a function of the delivery device 122. Forexample, the delivery device 122 may include a camera or other opticalscanning element. The delivery device 122 may activate the camera toscan an item 124 to be delivered. The item 124 may include a label 128identifying a recipient 190 of the item 124 or a delivery locationassociated therewith. The item 124 may include a scannable code 126.

In some implementations, the scannable code 126 may be amachine-readable code, e.g., optical code, one dimensional (1D) barcode, two dimensional (2D) bar code, recognizable text characters, or animage. In the case of a 2D bar code (also referred to as a “matrixcode”), the scannable code 126 may be a QR® or “quick response” code, anEZCode® bar code, a PDF417 or “portable data file” bar code, a highcapacity color bar code, etc. The scannable code 126 may be scannedusing optical techniques such as image scanning or infrared scanning.The scannable code may be transmitted using wireless techniques such asnear field communication, radio frequency identification tags,BLUETOOTH®, or other standardized or proprietary wireless messagingtechnology. The scannable code 126 may be affixed or otherwiseassociated with the item such that the item can be tracked from thesupplier, transportation, fulfillment center, and ultimate end user. Thescannable code 126 may encode or indicate an identifier for the item ordelivery information related to the item such as address, uniqueidentifier of a monitoring device 200, or other information used inidentifying or delivering the item 124.

The monitoring device 200 may be implemented as a camera or other datacollection device. The monitoring device 200 may be placed to monitor adelivery location. In some implementations, the monitoring device 200may be place near a door 160. The monitoring device 200 may be placedbehind the door 160 or in an area in front of the door 160. Themonitoring device 200 preferably collects data to identify entry andexit activity at the delivery location.

The door 160 may include a handle 164. The handle 164 may be manuallyoperated to disengage a locking mechanism 166. Upon disengagement of thelocking mechanism 166, the door 160 may open. In some implementations,the door 160 may be an automated door that, upon unlocking, opens usinga mechanical opening system. The door 160 may include a keyless lockcontroller 162 (e.g., a smart lock). The keyless lock controller 162 maybe an electronic device that can send and receive wireless signals suchas via ZIGBEE™, Z-WAVE®, or other local area network protocols. Thekeyless lock controller 162 may receive lock or unlock command messages.These messages may cause the keyless lock controller 162 to engage ordisengage the lock 166 without using the handle 164. In someimplementations, the keyless lock controller 162 may include a key pador other input element to receive an entry code to control the lock 166.

The keyless lock controller 162 may receive control signals from themonitoring device 200. The monitoring device 200 may include a firstwireless transceiver 210 for communications via local area networkprotocols. The monitoring device 200 may include a second wirelesstransceiver 208 for communications via a wide area network (e.g., theInternet or a cellular network) either directly or via a router (notshown). The first wireless transceiver 210 and the second wirelesstransceiver 208 may be commonly implemented in a multiband transceiverselectively configured to communicate via different wireless protocols.The monitoring device 200 may also transmit wireless signals using apersonal area network protocol such as a BLUETOOTH® Low Energy 4.0standard based protocol. These signals may be broadcasted to apredetermined area such as near the door 160. In this way, informationincluded in the broadcast signals may be used to verify proximity of adevice to the monitoring device 200 and, by association, the deliverylocation.

The monitoring device 200 may transmit monitoring data such as imagedata, video data, audio data, or the like collected by a sensor 202 themonitoring device 200. The monitoring data may be transmitted via thesecond wireless transceiver 208, via the wide area network, to theremote access server 150. The remote access server 150 may store themonitoring data in a data store.

As used herein a “data store” may be embodied in hard disk drives, solidstate memories and/or any other type of non-transitory computer-readablestorage medium accessible to or by a device such as an access device,server, or other computing device described. A data store may also oralternatively be distributed or partitioned across multiple local and/orremote storage devices as is known in the art without departing from thescope of the present disclosure. In yet other embodiments, a data storemay include or be embodied in a data storage web service.

The remote access server 150 may transmit control messages to themonitoring device 200. For example, the remote access server 150 maytransmit a message causing the monitoring device 200 to begin collectingmonitoring data. In some implementations, the monitoring device 200 maytransmit one or more acknowledgement messages to the remote accessserver 150 indicating a response to or result of a control message. Insome implementations, the acknowledgement may be included in a messagewith monitoring data.

The remote access server 150 may transmit access notification messagesto an access device 192 associated with the recipient 190. The accessdevice 192 may be an electronic communication device configured totransmit and receive machine readable messages such as email, textmessages, messages to activate an application or function of the accessdevice 192, or delivery alerts as described herein. Non-limitingexamples of the access device 192 include a personal computing device,laptop computing device, hand held computing device, terminal computingdevice, mobile device (e.g., mobile phones or tablet computing devices),wearable device configured with network access and program executioncapabilities (e.g., “smart eyewear” or “smart watches”), wirelessdevice, electronic reader, media player, home entertainment system,gaming console, set-top box, television configured with network accessand program execution capabilities (e.g., “smart TVs”), or some otherelectronic device or appliance. The messages may be formatted accordingto a standardized protocol such as TCP/IP, HTTP, FTP, or the like. Thetransmission may be sent wired, wireless, or hybrid wired-wirelessnetworks.

The access device 192 may present an interface including one or morecontrol elements to receive access permission inputs. The accesspermission inputs may identify periods of time when access should orshould not be granted for a delivery location. The remote access server150 may receive the access permission inputs and store them in a datastore. The access permissions may be accepted if the recipient 190provides sufficient user credentials (e.g., username, password,biometrics, etc.).

FIG. 2 is a diagram showing illustrative communication paths betweendevices within a remote access system. The diagram of FIG. 2 showscommunication paths between the delivery device 122, the remote accessserver 150, the monitoring device 200, the keyless lock controller 162,a core network 290, a base station 250, and a wireless router 240. Itwill be appreciated that other intermediary elements may be included.For the sake of clarity, these intermediaries have been omitted fromFIG. 2 as well as the description thereof

The delivery device 122 may communicate using at least two differentcommunication protocols. A first protocol may be used for a first path222 between the monitoring device 200 and the delivery device 122. Thefirst protocol may be a personal area network protocol for transmittingmessages over short distances such as 5 or 10 feet. The personal areaprotocol may be a BLUETOOTH® based protocol such as that defined by theBLUETOOTH® 4.0 Low Energy standard. Devices within the personal areanetwork may transmit a discovery message to allow other, nearby devicesto identify and establish a connection therewith.

A second protocol may be used for a second path 220 between the deliverydevice 122 and the base station 250. The base station 250 may be a widearea network base station such as a cellular or satellite network basestation. In such instances, the second protocol may be a wide areanetwork protocol for transmitting messages over long distance such as0.5 miles, 5 miles, or 25 miles. Examples of cellular or satellitenetwork communication protocols include code division multiple access(CDMA), wideband CDMA (WCDMA), global system for mobiles (GSM), orlong-term evolution (LTE). Unlike the personal area network, the widearea network may require a device to register before transmitting orreceiving messages from other devices via the wide area network. Awireless network may be associated with a service area. The service areamay identify a physical space where messages can be communicated usingthe associated network. In general, the service area of a wide areanetwork may be greater than the service area of a local area network. Alocal area network may provide a service area that is greater than theservice area of a personal area network.

The base station 250 may establish a communication path 226 with thecore network 290. The core network 290 may be a wide area network suchas the Internet. The remote access server 150 may be attached to thecore network 290 via path 232. The remote access server 150 may beassigned an address, such as an IP address, when attached to the corenetwork 290 allowing other devices to find and exchange messagestherewith.

The delivery location may include a router 240. The router 240 may belinked to the core network 290 via a path 230. The path 230 may includea wired connection from the router 240 to a service provider such as aninternet service provider. Equipment of the internet service providermay complete the path 230 to the core network 290. The router 240 mayprovide a local area WI-FI® network. Devices located with the servicerange of the local area network may connect to the router 240 to obtaina connection to the core network 290. For example, the monitoring device200 may establish a path 228 with the router 240. As shown in FIG. 2,the monitoring device 200 may communicate with the remote access server150 using paths 228, 226, and 232.

Additional or alternate paths may be included. For example, themonitoring device 200 may include a cellular transceiver to establish apath 234 via the base station 250. This path 234 may be the primarycommunication path for the monitoring device 200 to the core network290. In some implementations, this path 234 may be a backup path thatcan be enabled upon failure of a primary path such as the path 228.

The monitoring device 200 may also include a communication path 224 withthe keyless lock controller 162. The communication path 224 may traversea wireless local area network including machine-to-machine optimizationssuch as Z-WAVE® or ZIGBEE™. The communication path 224 typicallyservices a range greater than that served by the path 222. This allowsthe communication path 224 to service an entire area (e.g., a home)rather than a limited portion of thereof. In some implementations, thecommunication path 224 may include BLUETOOTH® based technologies.

In some implementations, a communication path may be used to create abridge. For example, if the delivery device 122 loses connectivity tothe base station 250, the delivery device 122 may transmit messages tothe monitoring device 220 via the path 222 for transmission to the corenetwork 290 via the path 228 and the path 230. In such instances, themonitoring device 220 may forward all messages received from thedelivery device 122 or selected messages such as those related to theaccess request or item being delivered. The monitoring device 220 mayidentify and selectively filter messages based on header informationindicating a type for the message.

FIG. 3 is a diagram showing illustrative messaging between deviceswithin a remote access system. The diagram of FIG. 3 shows messagesbetween the delivery device 122, the remote access server 150, themonitoring device 200, and an access control device 306 such as thekeyless lock controller 162 shown in FIGS. 1 and 2. It will beappreciated that other intermediary elements may be included. For thesake of clarity, these intermediaries have been omitted from FIG. 3 aswell as the description thereof. The messages shown may be communicatedusing one or more of the communication paths shown in FIG. 2.

Via message 310, the delivery device 122 may transmit informationindicating the delivery device 122 is approaching a delivery locationfor an item. The message 310 may include information scanned from theitem to be delivered. The message 310 may be transmitted to the remoteaccess server 150. In some implementations, the message 310 may betransmitted when the item is loaded for delivery (e.g., at adistribution center). For example, the item may be included on adelivery itinerary generated by a route planning system. The deliveryitinerary may be provided to the delivery device 122 to guide thedelivery agent to the delivery locations.

The remote access server 150 may identify the delivery location based atleast in part on the message 310. For example, if the message 310includes item identification information, the remote access server 150may query a data store to retrieve the recipient address information. Insome implementations, the message 310 may include geospatial informationsuch as coordinates or an address of the intended delivery location.

The remote access server 150 may identify or generate a unique accessidentifier. The unique access identifier may be information associatedwith the delivery location that can be used to determine when thedelivery device 122 is near or at the delivery location. In someimplementations, the unique access identifier may be a device identifierfor the monitoring device 200 or the access control device 306. Examplesof device identifiers include media access control (MAC) address, mobileequipment identifier (MEID), international mobile equipmentidentity/identifier (IMEI), or electronic serial number (ESN). In someimplementations, it may be desirable to have a dynamic access identifiergenerated that can be assigned to a device (e.g., a monitoring device)and used to validate proximity for a predetermined period of time (e.g.,10 minutes).

Via message 315, the remote access server 150 may transmit the uniqueaccess identifier to the delivery device 122. The received unique accessidentifier may be stored by the delivery device 122 to compare with anidentifier detected at the delivery location. In implementations wherethe item is identified via an itinerary, the itinerary may include theunique access identifier for the delivery location and/or item to bedelivered thereto.

The monitoring device 200 may transmit, via message 320, a unique accessidentifier. In implementations where a device identifier is used, theunique access identifier may be included in a discovery messagebroadcast by the monitoring device 200. In some implementations, thetransmission may be caused by a control message received by themonitoring device 200 from the remote access server 150. The controlsignal may include the unique access identifier to transmit in themessage 320.

The delivery device 122 may compare the access identifiers received viathe message 315 and the message 320. If the identifiers match, then thedelivery device 122 can assume it is at the appropriate deliverylocation. The match may cause an adjustment of an interface on thedelivery device 122 to show control elements related to access control.For example, once the proximity of the delivery device 122 to thedelivery location is confirmed, a control element to request access tothe delivery location may be presented. When the agent is ready to makethe delivery, she may activate the control element to transmit a message325 to the remote access server 150 requesting the delivery location beunlocked. The request may include the unique access identifier forvalidation by the remote access server 150. The request may include acurrent location of the delivery device 122 for validation by the remoteaccess server 150. The delivery device 122 may include a GlobalPositioning System (GPS) receiver to determine its current location.

The remote access server 150 may determine whether the delivery locationis associated with any access restrictions. For example, a recipientassociated with the delivery location may specify specific times fordelivery or designate “do not disturb/enter” times. The preferences maybe for the delivery location, for a specific item, or for time duration(e.g., on vacation). The remote access server 150 may receive accessrestrictions from a data store. The data store may store the accessrestrictions in association with an identifier for the delivery locationor recipient. The remote access server 150 may identify the recipient ordelivery location for an item associated with the activation requestmessage 325 based at least in part on a value included in the message325. If a request to unlock is received during such times or for an itemassociated with such times, the remote access server 150 may denyaccess. If the request is received at a time when the access request isallowed, the remote access server 150 may permit access, assuming allother preconditions are met.

The remote access server 150 may transmit a message 330 to themonitoring device 200 to activate the monitoring device 200 to an accessstate. Activating the monitoring device 200 may include transmitting acontrol signal to initiate recording. Activating the monitoring device200 may include transmitting a control signal to rotate or adjust thefield of monitoring of the monitoring device 200 to a door or other areawhere the entry will occur. The access state may be identified via aconfiguration stored in association with an identifier of the deliverylocation or recipient associated with the delivery location.

The remote access server 150 may receive a message 335 from themonitoring device 200 confirming that the access state is achieved. Thisensures that the monitoring device 200 is adequately adjusted to providea desired level of monitoring at the delivery location. The confirmationmay include monitored data such as image data, video data, audio data,or the like. In some implementations, the remote access server 150 mayanalyze data received via the message 335. For example, the content ofan image may be analyzed to ensure the recording is capturing anexpected scene and has not been obstructed or is otherwise capturing anunintended view. The analysis may include color analysis of the image(e.g., is the image all black or white; average contrast; averagebrightness; etc.). In some implementations, the analysis may compare aseries of images or frames of video. For example, the monitoring device200 may include an illuminator that can emit different colors of light.The illuminator may be activated to emit a pattern of light that can bedetected in images received by the remote access server 150. If theimages are consistent with the pattern of light, then the monitoringdevice 200 may be properly configured. The self-testing may be performedby the monitoring device 200 alone or in concert with the remote accessserver 150.

Once the remote access server 150 confirms the proper monitoring stateis achieved, the remote access server 150 may transmit a message 340 tothe monitoring device 200 indicating that access is granted. Themonitoring device 200 may, in turn, transmit a grant access message tothe access control device 306. The grant access message 345 may cause alock to unlock, a door to open, or disabling of another or additionalfeatures that secure the delivery location. FIG. 3 shows one accesscontrol device 306, but the grant access message 345 may be broadcast tomultiple access control devices and used to configure the respectivestates to permit access to the delivery location for delivery of theitem.

After the agent has delivered the item, the delivery device 122 maypresent a control element to indicate that the item has been delivered.Upon activation of such a control element, a task completed message 350may be transmitted to the remote access server 150. The message 350 mayinclude an identifier for the delivery device 122, the item, or thedelivery location. The remote access server 150 may use the identifierto find the monitoring device 200 at the delivery location. If theidentifier for the delivery device 122 is provided in the message 350,the remote access server 150 may compare the identifier with informationreceived in the unlock request (e.g., message 325). If the itemidentifier is provided in the message 350, the delivery location may beidentified based on the item identifier. The monitoring device 200 maybe associated with the delivery location and thus identified.

Having identified the monitoring device 200, the remote access server150 may transmit a message 355 to terminate access to the deliverylocation. The terminate access message may cause the monitoring device200 to transmit a message 360 to the access control device 306 to securethe delivery location. For example, if the access control device 306 isa keyless lock controller, the message 360 may cause the controller tore-engage the lock. Confirmation messages (not shown) may be transmittedby the access control device 306 or the monitoring device 200 toindicate that the delivery location has been secured.

Once the remote access server 150 confirms the delivery location hasbeen secured, a deactivate access state message 365 may be transmittedto the monitoring device 200. The message 365 may cause the monitoringdevice 200 to terminate collection of data (e.g., video recording) atthe delivery location.

The monitoring device 200 is discussed as both a sensor (e.g., camera)and a communications coordination device for exchanging messagesbetween, for example, the access control device 306 and the remoteaccess server 150. In some implementations, these functionalities may beseparated into distinct devices. For example, a monitoring hub may beincluded at the delivery location and configured to coordinate messagingbetween the remote access server 150 and a variety of devices at thedelivery location such as one or more sensors or one or more accesscontrol devices. In some implementations, the communications functionsmay be provided by a device coupled to the monitoring device 200. Forexample, a Z-WAVE® adapter may be connected to a peripheral port (e.g.,Universal Serial Bus port) of the monitoring device 200. The peripheralport may provide data and power connectivity for the communicationadapter (e.g., Z-WAVE® adapter).

FIG. 4 is a flow diagram depicting an example method of remote accessauthentication and authorization. The method 400 may be implemented inwhole or in part by the devices described such as the remote accessserver 150 or the delivery device 122. The method 400 illustrates how adelivery device can be authenticated and authorized to access a deliverylocation to deliver an item.

The method 400 may begin at block 402 with the assumption that an itemis en route for delivery to a location. At block 404, the remote accessserver 150 may receive an item identifier from the delivery device 122.The item identifier may be scanned by the delivery device 122. Thedelivery agent 120 may have provided user credentials to access thedelivery device 122. An identifier for the delivery agent may beincluded in a message with the item identifier. In some implementations,the item identifier may be associated with a parcel containing multipleitems. The receiving at block 404 may be via a wide area network.

At block 406, the remote access server 150 may determine whether thedelivery device 122 is authorized to deliver the item associated withthe item identifier. The determination may include confirming thecredentials of the delivery agent 120 or authenticity of the deliverydevice 122. The confirming may include comparing a security token,shared secret, or other identifying information to confirm that thedelivery agent 120 and delivery device 122 are permitted access to theremote access server 150. The determination at block 406 may includeretrieving order information for the item such as from an ordermanagement system. The order information may identify a recipientlocation for the item. If the recipient location does not correspond tothe current location of the delivery device 122, the authorizationdetermination at block 406 may be negative. In some implementations, thedetermination may include retrieving routing information for thedelivery device 122 such as from a route planning server. The routinginformation may identify a series of locations where deliveries will bemade. If the routing information does not include an entry associatedwith the item identifier, the determination at block 406 may benegative.

If the determination at block 406 is negative, the method 400 mayproceed to block 440. At block 440, the remote access server 150 maytransmit a delivery alert for the item. Transmitting a delivery alertmay include notifying the shipper of the item. For example, a deliveryalert indicating that the item was placed on the wrong delivery vehiclemay be transmitted to a route planning server. A delivery alert may betransmitted to the delivery device 122. For example, if the item wasgiven to the delivery agent 120 in error, the alert may cause theinterface of the delivery device 122 to present a message indicatingthat delivery of the item should be skipped and the agent may proceed toscan another item for delivery. A delivery alert may be transmitted tothe recipient. In some instances, the authorization may fail due to amalicious attempt to impersonate a delivery agent or delivery device. Insuch instances, it may be desirable to transmit an alert to therecipient to heighten awareness for suspicious persons or items. Thetransmission may be via a wide area network such as a cellular network,satellite network, or the Internet. Once transmitted, the method 400 mayend at block 490.

Returning to block 406, if the delivery device 122 is authorized, atblock 408, the remote access server 150 may activate a monitoring deviceat the delivery location to detect an identifier for the deliverydevice. Activation at block 408 may include transmitting a controlmessage via a wide area network to the monitoring device 200. In FIG. 3,the messaging illustrated how the delivery device 122 may detect anidentifier for the monitoring device 200. In the method 400 shown inFIG. 4, an alternate approach is shown whereby the monitoring devicedetects the identifier of the delivery device 122. The activation atblock 408 may include a control message to enable a transceiver on themonitoring device such as a low energy BLUETOOTH® 4.0 standard basedtransceiver. The activation may include the expected identifier of thedelivery device 122. In some implementations, the activation at block408 may be omitted and the control message may be continuouslytransmitted according to a schedule (e.g., every 30 seconds, everyminute, etc.).

At block 410, the remote access server 150 may receive a detectionmessage from the monitoring device 200. The detection message mayindicate receipt of the identifier for the delivery device 122. In someimplementations, the detection message may include additionalinformation about the delivery device 122 such as a security code orother information to confirm the identity of the delivery device 122such as a media access control (MAC) address, a mobile equipmentidentifier (MEID), an international mobile equipment identity/identifier(IMEI), or an electronic serial number (ESN).

At block 412, the remote access server 150 may determine whether thedelivery device has been positively detected. The determination at block150 may include analyzing the detection message. For example, if the MACaddress of the delivery device is provided, the remote access server 150may compare a registry of MAC addresses for authorized delivery deviceswith the received MAC address. If the received MAC address is included,then the positive detection may be confirmed. In some implementations,the confirmation may include comparing a current location of thedelivery device 122 with the location of the monitoring device 200. Forexample, the delivery device 122 may register with a cellular network.The cellular network may use triangulate to identify a location for thedelivery device 122. The delivery device 122 may include positioninghardware such as a GPS receiver which may alternatively or additionallyprovide a location for the delivery device 122.

The location of the delivery device 122 may be compared to the locationof the monitoring device 200. If the locations correspond, then thedetection may be confirmed. The correspondence of the locations may bebased on a threshold distance between the two locations.

The determination at block 412 may be negative if the delivery device122 has not yet come close enough to the monitoring device 200 totransmit the identifier. For example, the delivery device 122 maytransmit the identifier at a range of 5 or 10 feet. If the deliverydevice 122 has not been detected, it may still be outside the limitedrange. This may be desirable to ensure the identification is confirmedwhen the delivery device 122 is proximate to the delivery location.Another reason the detection at block 412 may fail is because theincorrect identifier for the delivery location is presented.

To allow the method 400 to account for delay or random error, at block430 the remote access server 150 may determine whether an attemptthreshold has been exceeded. The threshold may be based on the number ofdetection messages received. The threshold may be based on time. Forexample, if an elapsed time from an access request exceeds an attempttime threshold, it may be determined that a delivery error or failuremay have occurred. If the determination at block 430 is negative, themethod 400 may allow further access attempts by returning to block 408.If the determination at block 430 is affirmative, the number of attemptsor excessive delay may indicate an error in the delivery. In suchinstances, the method 400 may proceed to block 440 to transmit adelivery alert as discussed herein.

Returning to block 412, if the remote access server 150 determines thedelivery device 122 is proximately located to the monitoring device 200,the remote access server 150 may transmit a message to the deliverydevice 122 to display a request access control element on an interface.The request access control element may be a button or swipe controlthat, when activated, causes the delivery device 122 to transmit arequest access message to the remote access server 150. The requestaccess message may include a security token, shared secret, or otheridentifying information to confirm the identity of the delivery agent120 and delivery device 122. This can ensure that the delivery agent 120is authorized and in a position to make the delivery once access to thedelivery location is granted.

At block 416, the remote access server 150 may receive the requestaccess message from the delivery device 122. The request access messagemay include an identifier for one or more of the delivery device 122,the item, or the delivery location. The remote access server 150 may usethis information to retrieve do not disturb preferences. The do notdisturb preferences may be established based on the item. For example,if a recipient at a delivery location does not wish to allow unattendeddelivery of perishable items, the recipient may indicate a do notdisturb preference for items of type perishable. As another example, therecipient may wish to deny access during specific times such as duringevening hours. The recipient may establish access control permissionsincluding a time period during which remote access requests will bedenied even if the delivery device 122 is properly authenticated. Theaccess control permissions may be stored in a memory or other data storeaccessible by the remote access server 150. An access control permissionmay be associated with the delivery location or an identifier therefor.

If the determination at block 418 is affirmative and a do not disturbcondition is applicable, the method 400 may proceed to block 440 totransmit a delivery alert for the item. The delivery alert may indicatethat do not disturb conditions have been applied. In someimplementations, the alert may include alternate delivery instructionsfor the delivery agent (e.g., return to depot; leave with neighbor) orthe recipient (e.g., pick up at depot; will retry at a later date).

If the determination at block 418 is negative, do not disturb conditionsmay not be applicable and remote access may be granted. At block 500,the method 400 may permit access to the delivery location.

FIG. 5 is a flow diagram depicting an example method of permittingaccess to a delivery location based at least in part on monitoringstatus. The method 500 may be implemented in whole or in part by thedevices described such as the remote access server 150 or the deliverydevice 122. The method 500 illustrates how the status of the monitoringdevices at a location can be used to determine whether to permit accessto an authorized delivery device.

The method 500 may begin at block 502 with the assumption that an itemis proximately located to the delivery location and the delivery agentis authorized to deliver. To further ensure the security of thedelivery, it may be desirable to ensure that a desired level ofmonitoring is activated before allowing entry to the delivery location.

At block 504, the remote access server 150 may identify an accessmonitoring configuration for the delivery location. Because eachdelivery location may include different monitoring devices, it may bedesirable to identify which devices are available for a deliverylocation. The monitoring configuration may identify which devices and atwhat configuration to monitor the delivery location during unattendedaccess. The recipient associated with the delivery location may providea custom access monitoring configuration to allow monitoring of thedelivery location at a specified level. For example, the accessmonitoring configuration may identify a camera installed near a door foraccess monitoring. The access monitoring configuration may includespecific activation settings. For example, the camera may include anilluminator and the access monitoring configuration may specify a levelof illumination to activate for the camera. The access monitoringconfiguration may be stored in association with an identifier for thedelivery location.

At block 506, the remote access server 150 may determine whether thedelivery location is configured for the specified access monitoring. Thedetermination may include confirming communication channels with thespecified devices performing the monitoring. The determination at block506 may include testing the monitoring devices such as capturing samplemonitoring data to confirm desired operation.

The determination at block 506 may be based on a comparison between aresponse message received from one or more of the devices performing themonitoring and the access monitoring configuration. The comparison mayinclude verifying a status value for a monitoring device indicates aparticular monitoring state (e.g., recording, ready to record, batterylevel, orientation, field of view, etc.) specified by the accessmonitoring configuration. In some implementations, the determination atblock 506 may include comparing monitoring data (e.g., images, video,audio) or capture information related to the monitoring data (e.g.,frame rate, color profile, brightness, object recognition, etc. ormetric derived therefrom such as an average or moving average over time)with reference values identified using the access monitoringconfiguration. For example, to permit access to a delivery location, theaccess monitoring configuration may indicate that video captured at noless than 40 frames per second must be received. If the video datareceived is less than the specified threshold, the determination atblock 506 may be negative. As another example, the access monitoringconfiguration may identify a reference image of the delivery location.The reference image may be show a scene at the delivery location thatthe user wishes to capture during unattended access. The reference imagemay be compared to an image included in the monitoring data prior topermitting access to the delivery location. If the scene shown in theimage corresponds to the scene shown in the reference image, thedetermination at block 506 may be affirmative. Correspondence betweenimages may include comparing color histograms, locations of objectsdetected within the images, comparison of binary masked versions of theimages, or other image comparison techniques. Correspondence mayidentify differences or a degree of difference between the referenceimage and the monitored image. The number of differences or degree ofdifference may be compared to a correspondence threshold. Thedetermination at block 506 may be based on the comparison with thecorrespondence threshold.

If the determination at block 506 is negative, the method 500 mayproceed to block 508 to transmit one or more control messages toconfigure the monitoring devices identified in the access monitoringconfiguration for access monitoring. The control messages may cause thedevices to change power states (e.g., wake up from a sleep mode), adjustmonitoring area (e.g., activate a servo to rotate, pan, or zoom),perform a self-test, initiate collection of monitoring data (e.g., startrecording), or other adjustment. In some implementations, the controlmessage may be transmitted via a wide area network to a monitoring hubat the delivery location. The monitoring hub may then distribute thecontrol signals to respective devices at the delivery location using alocal area network or personal area network.

The monitoring hub or monitoring device identified by the one or morecontrol messages may provide a control message response. The controlmessage response may acknowledge receipt of a control message. Thecontrol message response may include a status indicator for themonitoring device. For example, if the monitoring device is a camera,the control message response may include information indicating thatrecording has been initiated.

Returning to block 506, if the delivery location is configured foraccess monitoring, at block 510, the remote access server 510 maytransmit a control message to allow access to the delivery location. Thecontrol message may be transmitted via a wide area network to amonitoring device. The monitoring device may then transmit an unlockmessage or release message via a local area network to one or moredevices to allow entry to the delivery location. In someimplementations, the unlock message may be transmitted to a keyless lockcontroller or other security device. In some implementations, the unlockmessage may be transmitted to an automatic door opener. In suchimplementations, the unlock message may include a distance to open thedoor. For example, if the item being delivered is a book, the door mayonly need to be opened a small amount to receive the item. To furtherenhance security of the delivery, the door may only be opened by anamount needed to receive the item. The amount may be determined by theremote access server 150 and included in the control message.

Because the remote access server 150 may not be actively monitoring thedelivery location once access has been granted, the remote access server150 may initiate a timer or otherwise record time to determine how longthe delivery location has been unlocked. At block 512, the remote accessserver 150 may determine whether the time that the delivery location hasbeen unlocked exceeds a threshold. The threshold may be between one andfive minutes. If the threshold has not been exceeded, the method 500 mayproceed to block 514. At block 514, a determination may be made as towhether the delivery is complete. The determination at block 514 may bebased on receipt of a message from the delivery device 122 indicatingthe delivery was completed. In some implementations the message mayinclude receiving an identifier for a new item for delivery from thedelivery device 122. In some implementations, it may be desirable toreceive an affirmative request to secure the location from the deliverydevice 122. For example, the delivery device 122 may present aninterface including a control element that, when activated, transmit themessage indicating delivery of the item is complete.

If the determination at block 514 is negative, the method 500 may returnto block 512 as described above. If the threshold at block 512 isexceeded, the method 500 may proceed to block 540. At block 540, theremote access server 150 may transmit a delivery alert for the item. Thetransmission at block 540 may be similar to that described withreference to block 440 in FIG. 4. In some implementations, the alert mayinclude one or more control messages to secure the delivery location.For example, a control message to close a door and/or secure a lock maybe transmitted to secure the delivery location as described herein.

Returning to block 514, if the remote access server 150 determines thatthe delivery is complete, it may be desirable to secure the deliverylocation. At block 516, the remote access server 150 may transmit one ormore control messages to secure the delivery location. The messages mayinclude transmitting a message to the monitoring device via a wide areanetwork. The monitoring device may in turn transmit a message via alocal area network to one or more devices to secure the deliverylocation. The message may include a request to close a door, enable alock, or the like.

At block 518, the remote access server 150 may confirm that the deliverylocation is secured. The confirmation may include receiving anacknowledgement from a monitoring device at the delivery location. Theconfirmation may include transmitting a request for status to one ormore of the devices at the delivery location and receiving a statusresponse. The response or acknowledgment may include informationindicating that the device is secured. If the devices associated withthe delivery location report a secured state, the determination at block518 may be affirmative.

Having secured the location, the monitoring of the delivery location maythen be adjusted to the pre-delivery configuration. At block 520, theremote access server 150 may transmit one or more control messages tothe monitoring devices that were activated to monitor the delivery. Theone or more control messages may change the monitoring state of themonitoring devices (e.g., stop recording; turn on motion activatedmonitoring). A control message may be transmitted via a wide areanetwork to a specific monitoring device to be adjusted. In someimplementations, the control message may be transmitted to onemonitoring device for further dissemination via the local area networkat the delivery location. The method 500 may end at block 590. Themethod 500 ensures that monitoring is activated while the deliverylocation is unsecured. A failure in monitoring may cause the access tobe denied or transmission of a delivery alert to quickly identify apotential problem.

FIG. 6 is a block diagram of an illustrative computing device that mayimplement one or more of the access control features described. Thecomputing device 600 may implement the methods or messaging shown in ofFIG. 3, 4, or 5. The computing device 600 can be a server or othercomputing device, and can comprise a processing unit 602, a remoteaccess processor 630, a network interface 604, a computer readablemedium drive 606, an input/output device interface 608, and a memory610. The network interface 604 can provide connectivity to one or morenetworks or computing systems. The processing unit 602 can receiveinformation and instructions from other computing systems or servicesvia the network interface 604. The network interface 604 can also storedata directly to memory 610. The processing unit 602 can communicate toand from memory 610 and output information to an optional display 618via the input/output device interface 608. The input/output deviceinterface 608 can also accept input from the optional input device 620,such as a keyboard, mouse, digital pen, microphone, mass storage device,etc.

The memory 610 contains computer program instructions that theprocessing unit 602 executes in order to implement one or moreembodiments. The memory 610 may include RAM, ROM, and/or otherpersistent, non-transitory computer readable media. The memory 610 canstore an operating system 612 that provides computer programinstructions for use by the processing unit 602 or other elementsincluded in the computing device in the general administration andoperation of the computing device 600. The memory 610 can furtherinclude computer program instructions and other information forimplementing aspects of the present disclosure.

For example, in one embodiment, the memory 610 includes a remote accessconfiguration 614. The remote access configuration 614 may include thethresholds, authentication information (e.g., encryption keys, tokens,device identifiers etc.), or other predetermined or configurable valuesdescribed above. The remote access configuration 614 may store specificvalues for a given configuration. The remote access configuration 614may, in some implementations, store information for obtaining values fora given configuration element. For example, a delivery deviceauthentication service may be specified as a network location (e.g.,URL) in conjunction with username and password information to access thenetwork location to obtain or verify a delivery device or propertythereof (e.g., location, associated delivery agent, route, or deliverymanifest). The remote access configuration 614 may be used by the remoteaccess processor 630 to implement one or more of the aspects describedherein. In some implementations, the remote access processor 630 mayinclude specific computer executable instructions that cause thecomputing device 600 to perform one or more of the remote access controlfeatures described.

The memory 610 may also include or communicate with one or moreauxiliary data stores, such as data store 622. The data store 622 mayelectronically store data regarding the item, the delivery agent, thedelivery device, the delivery location, monitoring devices, accesscontrol configurations for locations or devices, do not disturb rules,and the like.

The elements included in the computing device 600 may be coupled by abus 690. The bus 690 may be a data bus, communication bus, or other busmechanism to enable the various components of the computing device 600to exchange information.

In some embodiments, the computing device 600 may include additional orfewer components than are shown in FIG. 6. For example, a computingdevice 600 may include more than one processing unit 602 and computerreadable medium drive 606. In another example, the computing device 602may not be coupled to the display 618 or the input device 620. In someembodiments, two or more computing devices 600 may together form acomputer system for executing features of the present disclosure.

In one example implementation of the features described, a user mayinstall a smart lock or other keyless access control device on a door toher home or other delivery location and place a smart camera or otherremote controlled monitoring device inside the delivery location facingthe door. The user may request delivery an item using in-home delivery.When the delivery agent arrives at the door at the delivery location,the agent may first knock or ring the doorbell. If there is no answer,the agent may use a delivery device to scan the item and a deliveryapplication executing on the delivery device may transmit a request viaa cellular network to request the door to be unlocked. The system mayverify that the correct driver is at the door and transmit one or morecontrol messages to turn on the smart camera, unlock the door, andrecord the item being placed inside and the door being shut. Anotification confirming the delivery, including, in someimplementations, the video, may be transmitted to the user. The user canchoose a service time window at checkout and the system may grant accessto the service provider during that time. In such implementations, theuser may control the terms of unattended delivery. In someimplementations, the user may transmit a message to the access server todeny all access requests for the delivery location.

Depending on the embodiment, certain acts, events, or functions of anyof the processes or algorithms described herein can be performed in adifferent sequence, can be added, merged, or left out altogether (e.g.,not all described operations or events are necessary for the practice ofthe algorithm). Moreover, in certain embodiments, operations or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules, routines, andalgorithm steps described in connection with the embodiments disclosedherein can be implemented as electronic hardware, or as a combination ofelectronic hardware and executable software. To clearly illustrate thisinterchangeability, various illustrative components, blocks, modules,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as specializedhardware, or as specific software instructions executable by one or morehardware devices, depends upon the particular application and designconstraints imposed on the overall system. The described functionalitycan be implemented in varying ways for each particular application, butsuch implementation decisions should not be interpreted as causing adeparture from the scope of the disclosure.

Moreover, the various illustrative logical blocks and modules describedin connection with the embodiments disclosed herein can be implementedor performed by a machine, such as a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. A deliveryaccess device (e.g. remote access server or delivery device) can be orinclude a microprocessor, but in the alternative, the delivery accessdevice can be or include a controller, microcontroller, or statemachine, combinations of the same, or the like configured toauthenticate and authorize remote access for delivery of an item. Adelivery access device can include electrical circuitry configured toprocess computer-executable instructions. Although described hereinprimarily with respect to digital technology, a delivery access devicemay also include primarily analog components. For example, some or allof the access control algorithms or interfaces described herein may beimplemented in analog circuitry or mixed analog and digital circuitry. Acomputing environment can include a specialized computer system based ona microprocessor, a mainframe computer, a digital signal processor, aportable computing device, a device controller, or a computationalengine within an appliance, to name a few.

The elements of a method, process, routine, interface, or algorithmdescribed in connection with the embodiments disclosed herein can beembodied directly in specifically tailored hardware, in a specializedsoftware module executed by a delivery access device, or in acombination of the two. A software module can reside in random accessmemory (RAM) memory, flash memory, read only memory (ROM), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), registers, hard disk, aremovable disk, a compact disc read-only memory (CD-ROM), or other formof a non-transitory computer-readable storage medium. An illustrativestorage medium can be coupled to the delivery access device such thatthe delivery access device can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium can be integral to the delivery access device. The deliveryaccess device and the storage medium can reside in an applicationspecific integrated circuit (ASIC). The ASIC can reside in an accessdevice or other delivery access device. In the alternative, the deliveryaccess device and the storage medium can reside as discrete componentsin an access device or electronic communication device. In someimplementations, the method may be a computer-implemented methodperformed under the control of a computing device, such as an accessdevice or electronic communication device, executing specificcomputer-executable instructions.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without other input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y, or at least one of Z to each is present.

Unless otherwise explicitly stated, articles such as “a” or “an” shouldgenerally be interpreted to include one or more described items.Accordingly, phrases such as “a device configured to” are intended toinclude one or more recited devices. Such one or more recited devicescan also be collectively configured to carry out the stated recitations.For example, “a processor configured to carry out recitations A, B andC” can include a first processor configured to carry out recitation Aworking in conjunction with a second processor configured to carry outrecitations B and C.

As used herein, the terms “determine” or “determining” encompass a widevariety of actions. For example, “determining” may include calculating,computing, processing, deriving, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishing,and the like.

As used herein, the term “selectively” or “selective” may encompass awide variety of actions. For example, a “selective” process may includedetermining one option from multiple options. A “selective” process mayinclude one or more of: dynamically determined inputs, preconfiguredinputs, or user-initiated inputs for making the determination. In someimplementations, an n-input switch may be included to provide selectivefunctionality where n is the number of inputs used to make theselection.

As used herein, the terms “provide” or “providing” encompass a widevariety of actions. For example, “providing” may include storing a valuein a location for subsequent retrieval, transmitting a value directly tothe recipient, transmitting or storing a reference to a value, and thelike. “Providing” may also include encoding, decoding, encrypting,decrypting, validating, verifying, and the like.

As used herein, the term “message” encompasses a wide variety of formatsfor communicating (e.g., transmitting or receiving) information. Amessage may include a machine readable aggregation of information suchas an XML document, fixed field message, comma separated message, or thelike. A message may, in some implementations, include a signal utilizedto transmit one or more representations of the information. Whilerecited in the singular, it will be understood that a message may becomposed, transmitted, stored, received, etc. in multiple parts.

As used herein a “user interface” (also referred to as an interactiveuser interface, a graphical user interface, an interface, or a UI) mayrefer to a network based interface including data fields and/or othercontrols for receiving input signals or providing electronic informationand/or for providing information to the user in response to any receivedinput signals. A UI may be implemented in whole or in part usingtechnologies such as hyper-text mark-up language (HTML), ADOBE® FLASH®,JAVA®, MICROSOFT® .NET®, web services, and rich site summary (RSS). Insome implementations, a UI may be included in a stand-alone client (forexample, thick client, fat client) configured to communicate (e.g., sendor receive data) in accordance with one or more of the aspectsdescribed.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it can beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As can berecognized, certain embodiments described herein can be embodied withina form that does not provide all of the features and benefits set forthherein, as some features can be used or practiced separately fromothers. The scope of certain embodiments disclosed herein is indicatedby the appended claims rather than by the foregoing description. Allchanges that come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. (canceled)
 2. A computer-implemented method comprising: transmitting,by a delivery device to a remote access server, information indicatingthat the delivery device is approaching a delivery location for an item,wherein the information includes information identifying the item;receiving, by the delivery device from the remote access server, aunique identifier of a monitoring device at the delivery location;detecting, by the delivery device, an identifier broadcast by themonitoring device; determining, by the delivery device, that theidentifier broadcast by the monitoring device corresponds to the uniqueidentifier; displaying, by the delivery device, a first user interfaceincluding a first control element; in response to activation of thefirst control element, transmitting, by the delivery device to theremote access server, a request to access the delivery location, whereinthe request includes the unique identifier, the information identifyingthe item, and the delivery location; receiving, by the delivery devicefrom the remote access server, an indication that the delivery locationis accessible for delivery of the item; displaying, by the deliverydevice, a second user interface including a second control element; andin response to activation of the second control element, transmitting,by the delivery device to the remote access server, a request to securethe delivery location.
 3. The computer-implemented method of claim 2,wherein the unique identifier corresponds to the identifier detected atthe delivery location for a predetermined period of time.
 4. Thecomputer-implemented method of claim 2, wherein the identifier isbroadcast by the monitoring device via a first communication protocoland the unique identifier is received by the delivery device from theremote access server via a second communication protocol that isdifferent than the first communication protocol.
 5. Thecomputer-implemented method of claim 2 further comprising, in responseto activation of the first control element: reading, by the deliverydevice, a scannable code from the item, wherein the scannable codeencodes at least one of the unique identifier, the informationidentifying the item, or the delivery location.
 6. Thecomputer-implemented method of claim 2, wherein the request to accessthe delivery location that is transmitted by the delivery device andincludes the unique identifier confirms that the delivery device iswithin proximity of the delivery location for the item.
 7. Thecomputer-implemented method of claim 2 further comprising displaying, bythe delivery device following transmitting the request to access thedelivery location, an instruction to announce arrival at the deliverylocation.
 8. The computer-implemented method of claim 2, wherein therequest to access the delivery location includes the unique identifier,the information identifying the item, the delivery location, andinformation confirming the identity of at least one of the deliverydevice or an agent using the delivery device.
 9. Thecomputer-implemented method of claim 2 further comprising receiving, bythe delivery device, a delivery alert including at least one ofalternate delivery instructions or additional delivery instructions fordelivering the item.
 10. The computer-implemented method of claim 2further comprising receiving, by the delivery device from a routeplanning system, a delivery itinerary including the item.
 11. A deliverydevice comprising: an optical scanning device; a memory storing specificcomputer-executable instructions; and a processor in communication withthe optical scanning device and the memory, wherein the processor isconfigured by the specific computer-executable instructions to at least:transmit, to a remote access system, information indicating that thedelivery device is in a proximity of a delivery location for an item;receive, from the remote access system, a unique identifier of amonitoring device at the delivery location; determine that an identifierbroadcast by the monitoring device at the delivery location correspondsto the unique identifier; transmit a request to access the deliverylocation, wherein the request includes the unique identifier,information identifying the item, and the delivery location; receive anindication that the delivery location is accessible for delivery of theitem; and transmit a delivery notification.
 12. The delivery device ofclaim 11, wherein the processor is further configured by additionalspecific computer-executable instructions to at least store, in thememory, the unique identifier.
 13. The delivery device of claim 11,wherein the unique identifier corresponds to the identifier detected atthe delivery location for a predetermined period of time.
 14. Thedelivery device of claim 11, wherein the unique identifier comprises atleast one of a media access control address, a mobile equipmentidentifier, an international mobile equipment identifier, or anelectronic serial number.
 15. The delivery device of claim 11, whereinthe processor is further configured by additional specificcomputer-executable instructions to at least transmit a discoverymessage to the monitoring device.
 16. The delivery device of claim 11,wherein the processor is further configured by additional specificcomputer-executable instructions to at least activate the opticalscanning device to read a scannable code from the item, wherein thescannable code encodes at least one of the unique identifier, theinformation identifying the item, or the delivery location.
 17. Thedelivery device of claim 11, wherein the processor is further configuredby additional specific computer-executable instructions to at leastreceive the identifier broadcast by the monitoring device via a firstcommunication protocol.
 18. The delivery device of claim 17, wherein theprocessor is further configured by additional specificcomputer-executable instructions to at least transmit, to the remoteaccess system, the request to access the delivery location via a secondcommunication protocol that is different than the first communicationprotocol.
 19. The delivery device claim 17, wherein the processor isfurther configured by additional specific computer-executableinstructions to at least transmit, to the monitoring device, the requestto access the delivery location via the first communication protocol sothat the monitoring device can forward the request to access thedelivery location to the remote access system.
 20. The delivery deviceof claim 11, wherein the delivery notification comprises at least one ofa notification that delivery has been completed or a notificationrequesting that the delivery location be secured.
 21. The deliverydevice of claim 11, wherein the delivery notification includes at leastone of information identifying the delivery device, the informationidentifying the item, or the delivery location.